|
There are a few options when turning on tracing and logging. You can get severe errors and system errors as well as package specific tracing (if enabled). Logging/tracing usually found in /WebSphere/AppServer/profiles//logs/. See ... |
|
==Where to look for exceptions or errors==
db2diag.log About DB2 diagnostic log (db2diag.log) files: [[http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.pd.doc/doc/t0020814.htm|Setting the diagnostic log file error capture level] Related ... |
|
Using the Information Center, there is a page about http:publib.boulder.ibm.cominfocenterwmbhelpv6r0m0topiccom.ibm.support.core.doctopicsgettingfixes.htmGetting Fixes. A product fix might be available to resolve your problem. Is it running
Make sure the Event Broker is started, ... |
|
Where to look for errors (SystemOut, SystemErr, ffdc)
Loggingtracing usually found in WebSphereAppServerprofilesprofilenamelogs. See Logging and tracing at the Info Center. Server logs: Look in system error logs, found in ... |
|
For debugging the Sametime 8.0 Client, we have two options. Help Support View Log
Help Support View Trace How to turn the log level up By default, the Logging and Trace is set to only capture Severe errors. You can change this setting by changing the following file: ... |
|
Use the following articles to help you troubleshoot Sametime Advanced client, WebSphere Application Server, Event Broker, and DB2 components. http:www10.lotus.comlddstwiki.nsfdxHowtoturntheloglevelupTroubleshooting the Sametime Advanced 8 Client ... |